Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Presumably, this will require an RFC to properly stabilise, but this seems simple enough to warrant opening a PR. I doubt the API would be substantially different from the one I've provided, as it's very simple.
Basically, there are a few things in the standard library that have a
try_clonemethod, and it seems very reasonable to add aTryClonetrait as an analogue toTryFromandTryInto. I've personally run into a few cases where it'd be useful to have a trait like this, although again, it's up to others on whether this is useful.A few unanswered questions:
#[derive(TryClone)]even make sense? What would the error type be?try_clone_from? What would the behaviour be if the clone fails?